
Yes, it's possible to compile and run cassio on Windows, with some
caveats.

If you can't or don't want to compile cassio, you can find binary releases
for Windows on the cassio web site at http://www.urchlay.com/cassio/

If you're using a binary release, skip to "Running cassio.exe", below.


Compiling cassio.exe
--------------------

For compilation on a Windows host, you'll need to install Cygwin,
including its suite of GNU development tools (at minimum, you'll need
GNU make and gcc; bash, sed, and grep are highly recommended) [1].

For cross-compiling a Windows executable on a Linux host, you'll need a
cross-compiler capable of creating Cygwin-compatible Windows executables.
You can build one with crosstool (and a little bit of manual fixing, in
my case), or install one from your distribution's package repository,
if there is one. Once you've got the cross-compiler installed, have
a look at the Makefile: there are "crosswin" and "winzip" targets for
building cassio.exe, and a CROSSBIN variable that should point to the
bin directory of your cross-compiler, wherever you installed it.


Running cassio.exe
------------------

If you downloaded a binary release [3], it comes as a zip file. Extract it
somewhere like "C:\cassio" or wherever you like. Make sure you extract
the whole archive ("Extract all" in WinZip), not just cassio.exe: it
requires the cygwin1.dll file to be in the same place as cassio.exe.

There is no installer or setup.exe! Just copy cassio.exe and cygwin1.dll
to some convenient place, and/or create a shortcut for it on your desktop.

To run cassio.exe, you'll need cygwin1.dll in the same directory
("folder") as cassio.exe, or perhaps in C:\Windows\System or
similar. Unfortunately this is a rather large (1.7+ megabyte) DLL file...
not that bad on a modern system with modern-sized hard disks, but it
makes the binary releases take a while to download... I'm not sure how
compatible the different releases of cygwin1.dll are, so if you already
have a cygwin1.dll somewhere in your C:\Windows directory, don't replace
it with the one that comes with cassio (you may break other apps that
use the system-wide DLL).

cassio doesn't use the registry or any ini files, so you can move it
around on your drive without causing any problems, so long as cygwin1.dll
is kept in the same place as cassio.exe (or in a system-wide location).

For simple .cas image file transfers, you can run cassio by drag-and-drop,
or by associating .cas images with cassio.exe (see below). However, for
image analysis/repair, you'll have to run cassio from a command prompt
("cmd" or "command.com").

Usage is almost exactly as the Linux version. You can refer to the serial
ports as either the Linux-like /dev/ttyS0 and /dev/ttyS1, or the DOS-like
COM1 and COM2. [4]

The main differences from the Linux version are:

- Running cassio with no parameters will display the usage message
instead of reading from stdin. This is to avoid confusing people who
try to double-click the executable (it would just hang, waiting for the
user to *type* a .cas image!). You can still read from standard input
by giving a "-" (hyphen) as the input filename.

- Instead of exiting when finished, cassio will display a "Press Enter to
exit" message. This prevents cassio's window from closing when it exits
(especially useful for drag-and-drop).

- Drag and drop is supported [5]. If you need to specify extra arguments or
a different serial port from the default, you can create a batch file
that runs cassio with the right arguments, or a shortcut on the desktop.

- It should also be possible to associate .cas files with cassio,
so you can double-click a cassette image to send it to the Atari.
cassio doesn't do this association itself; you can use "Open with" on a
.cas file, select cassio.exe or your batch file, and check "Always use
this program to open this type of file" to do it manually.

- AtariSIO is not supported. Not really a limitation, since there is no
AtariSIO for Windows...

- Custom baud rates (other than 600) are not supported. I don't even
know if Windows supports nonstandard baud rates; if it does, I don't
know how to set them. If you do know, drop me a line...


Notes
-----

[1] You can NOT use MinGW or MS Visual Studio [2] to compile cassio!
It's written for UNIX-like environments, and it needs the UNIX
compatibility provided by Cygwin. This is my fault; I'm not a Windows
programmer (or even a user)... at some point, I plan to learn enough of
the Windows API to be able to ditch the Cygwin requirement and compile
with MinGW, but that day hasn't arrived yet...

[2] It *may* be theoretically possible to compile with Visual Studio and
MS Services for UNIX, but I have no idea whether this would work. If you
do get this to work, I'd love to know how, so I can document it here,
but please don't ask me for help with it; I've got no idea :)

[3] The binary releases are compiled on a Linux machine with a
cross-compiler version of cygwin, and tested on my old Pentium 120 laptop
that runs Windows 95.

[4] If you get "permission denied" errors, you may have to run cassio.exe
as the Administrator user, or set things up so normal users can use the
serial ports. I don't know how to do this on Windows; sorry.

[5] Actually, drag-and-drop and filetype associations work just fine
on Linux/UNIX, too, if you're running something like KDE or Gnome.


--
B. Watson
urchlay (at) urchlay (dot) com
Urchlay on www.atariage.com
